fix(deps): update module go.datum.net/datumctl to v0.16.0#14
Open
renovate[bot] wants to merge 1 commit into
Open
fix(deps): update module go.datum.net/datumctl to v0.16.0#14renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
c51724c to
9f4349f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.15.0→v0.16.0Release Notes
datum-cloud/datumctl (go.datum.net/datumctl)
v0.16.0Compare Source
The plugin system just got its ecosystem. In v0.15.0 you could install plugins from a single Datum-operated catalog. Now anyone — a community author, an open-source project, or an enterprise platform team — can publish their own catalog, and you can register, search, browse, and install across all of them through the same commands you already know. The curated datum catalog stays the trusted, zero-configuration default, so nothing changes if you never add one.
New: register third-party catalogs (
datumctl plugin index) (#224)Plugins can now come from more than one place. Add a community or internal catalog with a single command — and an explicit one-time trust decision so you always know what you're opting into.
New: search and install across every catalog (#224)
searchandinstallnow span every registered catalog at once, with clear official vs. third-party badges wherever a plugin appears — provenance is never ambiguous. Pin a specific release from any catalog when you need to.New: interactive marketplace browser (
datumctl plugin browse) (#224)Prefer to explore?
datumctl plugin browseopens an interactive view across all catalogs, each result clearly badged by source.For enterprises (#224)
Private internal catalogs are first-class. A new
datumctl plugin validatecommand lets authors check a manifest before publishing, and allow-list guardrails let platform teams scope which publishers are permitted — down to individual GitHub owners or repositories — with the policy re-enforced continuously, not just at the moment a catalog is added.Docs
brew truststep needed by newer Homebrew versions (#215).Full Changelog: datum-cloud/datumctl@v0.15.2...v0.16.0
v0.15.2Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/datumctl@v0.15.1...v0.15.2
v0.15.1Compare Source
What's Changed
New Contributors
Full Changelog: datum-cloud/datumctl@v0.15.0...v0.15.1
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.